Name an entity's own columns before the ones it inherits - #16

Follow-up to #15, found reviewing it.

What happens

Folding inherited properties gives every entity the columns it persists, in the order the class reads them — root down, base first. Two summaries then take the first few of that list, and on an application with a shared audit base the first few are the base's for every entity at once.

The agent context's entity table, measured on a base of six audit columns:

Not one of Invoice's own columns survived a five-slot window. Across a seven-entity fixture, six rows carried the identical five names — a table whose whole job is to tell entities apart, unable to. Customer kept one column by accident, because a required property outranks the rest.

The same eight-slot summary in the navigation section of the published documents had it too. One fix per reader, or the reader who gets missed keeps the defect.

Why the corpora in #15 could not have shown it

All three have thin bases. The shape that hurts is the one #13 named — an audit base wider than the entities under it — and no fixture had it. AuditedXpoSolution is that shape: six inherited columns against two or three own ones. It is kept apart from DeepXpoSolution, whose tests pin exact property lists on a base of one column; the inverted proportion is the whole point of the new one.

How it decides

InheritedFrom, added in #15 for a renderer that had not been written yet, is what the summaries sort by — own first, then the inherited ones in their existing ranking, filling whatever slots are left. OrderByDescending is a stable sort, so within each group the root-down order #15 established is preserved.

The fold itself is right and the full listings are unaffected: they still read root down, the way the class does. Only the two fixed-width summaries change, and only in which end of the list they spend their width on.

Deliberately out of scope: a [PersistentAlias] on a shared base now makes every descendant report calculated properties (XafDetailTools, HtmlExplainerGenerator). That is redundancy rather than loss — the alias does apply to the descendant — and it belongs with the editorial half of #14.

Verification

299 tests, 0 warnings. Three of the four new tests fail on main:

AnEntitysOwnColumnsSurviveAFixedWidthSummary   index 0: expected "Reference", got "CreatedBy"
RequiredColumnsStillOutrankTheRestOfTheEntitysOwn   index 1: expected "IssuedOn", got "CreatedBy"
TheNavigationSummaryNamesTheEntitysOwnColumnsFirstToo   StartsWith fails

The fourth, TheBaseItselfStillNamesItsOwnColumns, passes both before and after on purpose: it exists so nobody "fixes" this by hiding inherited properties, which would blank the base's own row — the same defect facing the other way.

🤖 Generated with Claude Code